From da7f5063bb269235f617fc78296043d276c4f3f5 Mon Sep 17 00:00:00 2001 From: Mathieu Poumeyrol Date: Mon, 27 Oct 2014 01:42:15 +0100 Subject: [PATCH] Two typos --- src/doc/config.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/doc/config.md b/src/doc/config.md index b4c38600e..d0669cba1 100644 --- a/src/doc/config.md +++ b/src/doc/config.md @@ -2,12 +2,12 @@ This document will explain how cargo's configuration system works, as well as available keys or configuration. For configuration of a project through its -manfest, see the [manifest format](manifest.html). +manifest, see the [manifest format](manifest.html). # Hierarchical structure Cargo allows to have local configuration for a particular project or global -configuration (like git). Cargo also extends this ability to a hirearchical +configuration (like git). Cargo also extends this ability to a hierarchical strategy. If, for example, cargo were invoked in `/home/foo/bar/baz`, then the following configuration files would be probed for: -- 2.30.2